Available dynamic tokens

There are two ways to get dynamic data from FunnelFlux to your pages:

Through a redirect link
Using our JavaScript

With redirect links this is quite simple as you can just add {token} to the URL or, better yet, use the data passing section, which has semantic lists available for you to search through, and already filters out tokens that don't work for that resource.

For getting token data from our JavaScript, you should refer to this article HERE and HERE.

Table of Available Tokens

Below is a list of all our tokens, split by their category.

User Identifiers

Data that is specific to a user and their tracking.

Name	Token	Pages	Conversions
Hit ID	`{hit}`	✅	✅
Visitor ID	`{visitor}`	✅	✅
External ID	`{external}`	✅	✅
User IP	`{ip}`	✅	✅
User-Agent	`{user-agent}`	✅	✅

General Tokens

These are general tokens that relate to internal FunnelFlux data like funnels, traffic source IDs, etc.

Name	Token	Pages	Conversions
Current Unix Time	`{timestamp}`	✅	✅
Funnel + Traffic Source Hash	`{tracking-fts}`	✅	⛔
Funnel Group ID	`{group-id}`	✅	⛔
Funnel Group Name	`{group-name}`	✅	⛔
Funnel ID	`{funnel-id}`	✅	✅
Funnel Name	`{funnel-name}`	✅	⛔
Referrer Domain	`{referrer-domain}`	✅	✅
Referrer URL	`{referrer}`	✅	✅
Tracking Domain	`{tracking-domain}`	✅	⛔
Traffic Source ID	`{trafficsource-id}`	✅	⛔
Traffic Source Name	`{trafficsource-name}`	✅	⛔
Traffic Source Campaign	`{campaign}`	✅	✅

Custom and URL Data

Custom strings and data passed into the URL buffer, i.e. entrance or action links.

Name	Token	Pages	Conversions
Custom String	N/A	✅	⛔
URL Data Field	`{data-name}`	✅	✅

Location and Connection (resolved from user IP)

All data that is resolved from our IP-geolocation provider. Using this data in redirect links or JS will slightly increase response times due to the lookup needed.

Name	Token	Pages	Conversions
ISP Name	`{isp}`	✅	✅
Connection Type	`{connection-type}`	✅	✅
Continent	`{continent}`	✅	✅
Country Code	`{country-code}`	✅	✅
Country Name	`{country-name}`	✅	✅
Region	`{region}`	✅	✅
City	`{city}`	✅	✅
User Latitude	`{latitude}`	✅	✅
User Longitude	`{longitude}`	✅	✅
User Timezone	`{timezone}`	✅	✅

Browser and Device (resolved from user-agent)

All data that is resolved from our device detection provider. Using this data in redirect links or JS will slightly increase response times due to the lookup needed.

Name	Token	Pages	Conversions
Browser Name	`{browser}`	✅	✅
Browser Language	`{browser-language}`	✅	✅
Browser Version	`{browser-version}`	✅	✅
Device Brand	`{brand}`	✅	✅
Device Type	`{device-type}`	✅	✅
Device Model Code	`{model}`	✅	✅
Device Model Name	`{model-name}`	✅	✅
Operating System	`{os}`	✅	✅
Operating System Version	`{os-version}`	✅	✅

Node-related Data

Data related to nodes/pages visited in the context of a funnel.

Name	Token	Pages	Conversions
Click Action Number	`{action-number}`	✅	⛔
Current Node ID	`{current-node-id}`	✅	⛔
Current Node Name	`{current-node-name}`	✅	⛔
Page ID	`{page-id}`	✅	✅
Page Name	`{page-name}`	✅	✅
Page URL	`{page-url}`	⛔	✅
Referring Node ID	`{referring-node-id}`	✅	⛔
Referring Node Name	`{referring-node-name}`	✅	⛔
Offer Source ID	`{offer-source-id}`	✅ Offers Only	⛔

Conversion Data

This is data specifically associated with conversions. Note External ID comes from the "external" tracking field and is captured when a user enters from a traffic source. It is repeated here since its critically used in conversion tracking.

Name	Token	Pages	Conversions
Conversion Timestamp	`{conversion-time}`	⛔	✅
Conversion Revenue	`{payout}`	⛔	✅
Conversion Transaction ID	`{txid}`	⛔	✅
External ID	`{external}`	✅	✅
Entrance Timestamp	`{entrance-timestamp}`	⛔	✅

Encrypting Token Data

In cases where you want to pass encrypted/hashed data, you can use our token modifiers.

Please see our article here.